Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1364

reference: 175-tree-1
name: 1364
tree-preservation-order: undefined
175-tpo-1
uprn
address-text
point: POINT (-0.944782 50.859295)
geometry: MULTIPOLYGON (((-0.944711 50.859288,-0.944714 50.859302,-0.944724 50.859314,-0.944739 50.859324,-0.944759 50.859331,-0.944781 50.859333,-0.944803 50.859331,-0.944823 50.859325,-0.944839 50.859315,-0.944849 50.859303,-0.944853 50.859289,-0.944850 50.859275,-0.944840 50.859263,-0.944825 50.859252,-0.944805 50.859246,-0.944783 50.859243,-0.944761 50.859245,-0.944741 50.859252,-0.944725 50.859261,-0.944715 50.859274,-0.944711 50.859288)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL